Red Hat OpenShift Platform using OpenShift UI

You can deploy the UCT-C Controller and Taps in the Red Hat OpenShift Platform using Helm Charts.

Refer to the following sections:

Prerequisites

■   To deploy, you should have Developer access in Red Hat OpenShift Platform.
■   To validate the deployment, you should have Administrator access.

Deployment of UCT-C Controller and Taps

To deploy UCT-C Controller and Taps, follow these steps:

1.   Using your Red Hat login credentials. log in to the Red Hat OpenShift online platform.
2. Select the drop-down on the top of the page and switch to Developer access.
3. Navigate to the Helm section, and select Create > Helm Release.
The Helm Charts screen appears.
4. From the All items search menu, browse and select Gigamon.
5. On the Gigamon-UCT-C landing page, select Create.
The Create Helm Release page appears.

Note:  The README content on the Gigamon-UCT-C landing page provides information on how to deploy the UCT-C Controller and Tap on a Kubernetes cluster using Helm Chart.

6. Specify the Helm Release name to create Helm Release
7. Select the appropriate release version from the drop-down menu. By default, the latest uploaded version of the release is displayed.
8. Select either Form view or YAML view for configuration and specify the created secret name in imagePullSecrets field.
9. In the uctcTap section:
a. Specify the socket location details in resources - crisocketvolume filed.

Note:  The socket location for commonly used CRIs are as follows:
docker - /var/run/docker.sock
containerd - /var/run/containerd/containerd.sock
cri-o - /var/run/crio/crio.sock

b. Specify the namespace.
c. Specify the following details in the ingress section:

  1. enabled - Select the check box to enable.

  2. annotations - Specify the annotations details (kubernetes.io/ingress.class and nginx.ingress.kubernetes.io/backend-protocol).

d. Enable the Create option and specify the serviceAccount name.
10. In uctcController section:
a. Specify the port value.
b. Specify the following details in certs field:

  1. ext_load_balancer - The external load balancer IP/DNS value to allow GigaVUE-FM to communicate with the UCT-C Controller within Kubernetes.

  2. k8s_cluster_url - Kubernetes cluster endpoint for GigaVUE-FM to access the control plane.
    Example: https://<kubernetesapiserverurl>:6443

c. Specify the service label name. For example: uctc-cntrl-service.
d. Specify the repository and pullPolicy details in the image field.
e. Update the namespace and fm_ip details.
11. Select Create to deploy the UCT-C solution.
12. To validate the deployment, switch to Administrator view and navigate to:
a. DaemonSets option to validate the UCT-C-Tap deployment.
b. Deployment option to validate the UCT-C-Controller deployment.